fix(scan): label ticker uptime as Node uptime#108
Conversation
uptime_seconds from /sentrix_status is the serving node's process uptime since its last restart (~4 days), not the chain age. The bare 'Uptime' label read as network uptime and looked wrong on a chain that is millions of blocks old. Relabel to make clear it is the node's uptime.
|
Warning Review limit reached
More reviews will be available in 10 minutes and 59 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
The live ticker showed 'Uptime: 4.1d', which reads as network/chain uptime. The value is uptime_seconds from /sentrix_status, which is the serving node's process uptime since its last restart (verified live: 353653s = 4.09 days), not the chain age (testnet is past 9.2M blocks, months old). Relabel to 'Node uptime' so it is not misread. Value and formatting are unchanged.